Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor!: split bls and secp256k1 private key #1471

Merged
merged 5 commits into from
Oct 12, 2023
Merged

Conversation

KaoImin
Copy link
Contributor

@KaoImin KaoImin commented Oct 11, 2023

What this PR does / why we need it?

This PR split the bls and secp256k1 private key.

The bls public key and secp256k1 used to keep a same private key and generate their own public key. Although there are no studies that show the safety risks of this behavior, we intend to change this. The config file is now add a bls_private_key field, this private key only used to sign the consensus messages.

Notice: The address in Validator list is calculate by secp256k1 public key, axon will never use bls public key to calculate address.

PR relation:

CI Settings

CI Usage

Tip: Check the CI you want to run below, and then comment /run-ci.

CI Switch

  • Web3 Compatible Tests
  • OCT 1-5 And 12-15
  • OCT 6-10
  • OCT 11
  • OCT 16-19
  • v3 Core Tests

CI Description

CI Name Description
Web3 Compatible Test Test the Web3 compatibility of Axon
v3 Core Test Run the compatibility tests provided by Uniswap V3
OCT 1-5 | 6-10 | 11 | 12-15 | 16-19 Run the compatibility tests provided by OpenZeppelin

@KaoImin KaoImin requested a review from a team as a code owner October 11, 2023 07:38
@KaoImin KaoImin requested review from jjyr and Simon-Tl October 11, 2023 07:38
@KaoImin

This comment was marked as off-topic.

@github-actions

This comment was marked as outdated.

@KaoImin KaoImin changed the title refactor: split bls and secp256k1 private key refactor!: split bls and secp256k1 private key Oct 11, 2023
@KaoImin KaoImin force-pushed the split-off-private-key branch from 7ec2f5c to 1471fcf Compare October 11, 2023 09:42
@KaoImin KaoImin requested a review from driftluo October 11, 2023 09:50
@KaoImin KaoImin force-pushed the split-off-private-key branch from 1471fcf to b56e345 Compare October 11, 2023 14:48
@KaoImin

This comment was marked as off-topic.

@github-actions
Copy link

CI tests run on commit:

CI test list:

  • Web3 Compatible Tests

Please check ci test results later.

driftluo
driftluo previously approved these changes Oct 11, 2023
devtools/chain/config.toml Show resolved Hide resolved
@KaoImin KaoImin requested a review from driftluo October 12, 2023 02:25
@KaoImin
Copy link
Contributor Author

KaoImin commented Oct 12, 2023

/run-ci

@github-actions
Copy link

CI tests run on commit:

CI test list:

  • Web3 Compatible Tests

Please check ci test results later.

@KaoImin

This comment was marked as off-topic.

@github-actions
Copy link

CI tests run on commit:

CI test list:

  • Web3 Compatible Tests

Please check ci test results later.

@KaoImin KaoImin enabled auto-merge October 12, 2023 02:51
@KaoImin KaoImin added this pull request to the merge queue Oct 12, 2023
Merged via the queue into main with commit a6fffed Oct 12, 2023
17 checks passed
@KaoImin KaoImin deleted the split-off-private-key branch October 12, 2023 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Question: Is it safe to use same private key in two or more algorithms?
4 participants